Apparatus, system, and method of communicating cellular quality of service (qos) information

ABSTRACT

For example, an apparatus may be configured to cause wireless communication station (STA) to set a cellular Quality of Service (QoS) index value in a cellular QoS index field to indicate a predefined setting of a set of a plurality QoS parameters for a cellular QoS traffic flow to be communicated by the STA over a Wireless Local Area Network (WLAN). For example, the apparatus may be configured to cause the STA to transmit a Stream Classification Service (SCS) request to an Access Point (AP) of the WLAN, the SCS request including an SCS descriptor element, the SCS descriptor element including the cellular QoS index field.

TECHNICAL FIELD

Aspects described herein generally relate to communicating cellularQuality of Service (QoS) information.

BACKGROUND

Devices in a wireless communication system may be configured tocommunicate according to communication protocols, which may beconfigured to support high-throughput data for users of wirelesscommunication devices.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative aspects.

FIG. 2 is a schematic illustration of a multi-link communication scheme,which may be implemented in accordance with some demonstrative aspects.

FIG. 3 is a schematic illustration of a multi-link communication scheme,which may be implemented in accordance with some demonstrative aspects.

FIG. 4 is a schematic illustration of a Stream Classification Service(SCS) descriptor element, in accordance with some demonstrative aspects.

FIG. 5 is a schematic illustration of a Quality of Service (QoS)characteristics element, in accordance with some demonstrative aspects.

FIG. 6 is a schematic flow-chart illustration of a method ofcommunicating cellular QoS information, in accordance with somedemonstrative aspects.

FIG. 7 is a schematic flow-chart illustration of a method ofcommunicating cellular QoS information, in accordance with somedemonstrative aspects.

FIG. 8 is a schematic illustration of a product of manufacture, inaccordance with some demonstrative aspects.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some aspects.However, it will be understood by persons of ordinary skill in the artthat some aspects may be practiced without these specific details. Inother instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer’s registers and/or memories into other data similarlyrepresented as physical quantities within the computer’s registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one aspect”, “an aspect”, “demonstrative aspect”,“various aspects” etc., indicate that the aspect(s) so described mayinclude a particular feature, structure, or characteristic, but notevery aspect necessarily includes the particular feature, structure, orcharacteristic. Further, repeated use of the phrase “in one aspect” doesnot necessarily refer to the same aspect, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some aspects may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, awearable device, a sensor device, an Internet of Things (IoT) device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a Wireless Video Area Network (WVAN),a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal AreaNetwork (PAN), a Wireless PAN (WPAN), and the like.

Some aspects may be used in conjunction with devices and/or networksoperating in accordance with existing IEEE 802.11 standards (includingIEEE 802.11-2020 (IEEE 802.11-2020, IEEE Standard for InformationTechnology-Telecommunications and Information Exchange between SystemsLocal and Metropolitan Area Networks-Specific Requirements; Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications, December, 2020); and/or IEEE 802.11be (IEEEP802.11be/D2.0 Draft Standard for Information technology—Telecommunications and information exchange between systems Local andmetropolitan area networks— Specific requirements; Part 11: Wireless LANMedium Access Control (MAC) and Physical Layer (PHY) Specifications;Amendment 8: Enhancements for extremely high throughput (EHT), May2022)) and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing Wi-Fi Specifications(including Wi-Fi QoS Management™ Specification Version 2.0, 21 October,2021) and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing cellular specificationsand/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPPLong Term Evolution (LTE) and/or future versions and/or derivativesthereof, units and/or devices which are part of the above networks, andthe like.

Some aspects may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multistandard radio devices orsystems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some aspects may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra-Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access(OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division MultipleAccess (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division MultipleAccess (SDMA), Extended TDMA (E-TDMA), General Packet Radio Service(GPRS), extended GPRS, Code-Division Multiple Access (CDMA), WidebandCDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®,Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband(UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G,4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks,3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates forGSM Evolution (EDGE), or the like. Other aspects may be used in variousother devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative aspects, a wirelessdevice may be or may include a peripheral that may be integrated with acomputer, or a peripheral that may be attached to a computer. In somedemonstrative aspects, the term “wireless device” may optionally includea wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device. The communication signal may be transmittedand/or received, for example, in the form of Radio Frequency (RF)communication signals, and/or any other type of signal.

As used herein, the term “circuitry” may refer to, be part of, orinclude, an Application Specific Integrated Circuit (ASIC), anintegrated circuit, an electronic circuit, a processor (shared,dedicated or group), and/or memory (shared, dedicated, or group), thatexecute one or more software or firmware programs, a combinational logiccircuit, and/or other suitable hardware components that provide thedescribed functionality. In some aspects, some functions associated withthe circuitry may be implemented by, one or more software or firmwaremodules. In some aspects, circuitry may include logic, at leastpartially operable in hardware.

The term “logic” may refer, for example, to computing logic embedded incircuitry of a computing apparatus and/or computing logic stored in amemory of a computing apparatus. For example, the logic may beaccessible by a processor of the computing apparatus to execute thecomputing logic to perform computing functions and/or operations. In oneexample, logic may be embedded in various types of memory and/orfirmware, e.g., silicon blocks of various chips and/or processors. Logicmay be included in, and/or implemented as part of, various circuitry,e.g. radio circuitry, receiver circuitry, control circuitry, transmittercircuitry, transceiver circuitry, processor circuitry, and/or the like.In one example, logic may be embedded in volatile memory and/ornon-volatile memory, including random access memory, read only memory,programmable memory, magnetic memory, flash memory, persistent memory,and the like. Logic may be executed by one or more processors usingmemory, e.g., registers, stuck, buffers, and/or the like, coupled to theone or more processors, e.g., as necessary to execute the logic.

Some demonstrative aspects may be used in conjunction with a WLAN, e.g.,a WiFi network. Other aspects may be used in conjunction with any othersuitable wireless communication network, for example, a wireless areanetwork, a “piconet”, a WPAN, a WVAN and the like.

Some demonstrative aspects may be used in conjunction with a wirelesscommunication network communicating over a sub-10 Gigahertz (GHz)frequency band, for example, a 2.4 GHz frequency band, a 5 GHz frequencyband, a 6 GHz frequency band, and/or any other frequency below 10 GHz.

Some demonstrative aspects may be used in conjunction with a wirelesscommunication network communicating over an Extremely High Frequency(EHF) band (also referred to as the “millimeter wave (mmWave)” frequencyband), for example, a frequency band within the frequency band ofbetween 20 Ghz and 300 GHz, for example, a frequency band above 45 GHz,e.g., a 60 GHz frequency band, and/or any other mmWave frequency band.

Some demonstrative aspects may be used in conjunction with a wirelesscommunication network communicating over the sub-10 GHz frequency bandand/or the mmWave frequency band, e.g., as described below. However,other aspects may be implemented utilizing any other suitable wirelesscommunication frequency bands, for example, a 5G frequency band, afrequency band below 20 GHz, a Sub 1 GHz (S1G) band, a WLAN frequencyband, a WPAN frequency band, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In some aspects,the antenna may implement transmit and receive functionalities usingseparate transmit and receive antenna elements. In some aspects, theantenna may implement transmit and receive functionalities using commonand/or integrated transmit/receive elements. The antenna may include,for example, a phased array antenna, a single element antenna, a set ofswitched beam antennas, and/or the like.

Reference is made to FIG. 1 , which schematically illustrates a system100, in accordance with some demonstrative aspects.

As shown in FIG. 1 , in some demonstrative aspects, system 100 mayinclude one or more wireless communication devices. For example, system100 may include a wireless communication device 102, a wirelesscommunication device 140, and/or one or more other devices.

In some demonstrative aspects, devices 102 and/or 140 may include amobile device or a non-mobile, e.g., a static, device.

For example, devices 102 and/or 140 may include, for example, a UE, anMD, a STA, an AP, a PC, a desktop computer, a mobile computer, a laptopcomputer, an Ultrabook™ computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, an Internet of Things(IoT) device, a sensor device, a handheld device, a wearable device, aPDA device, a handheld PDA device, an on-board device, an off-boarddevice, a hybrid device (e.g., combining cellular phone functionalitieswith PDA device functionalities), a consumer device, a vehicular device,a non-vehicular device, a mobile or portable device, a non-mobile ornon-portable device, a mobile phone, a cellular telephone, a PCS device,a PDA device which incorporates a wireless communication device, amobile or portable GPS device, a DVB device, a relatively smallcomputing device, a non-desktop computer, a “Carry Small Live Large”(CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC),a Mobile Internet Device (MID), an “Origami” device or computing device,a device that supports Dynamically Composable Computing (DCC), acontext-aware device, a video device, an audio device, an A/V device, aSet-Top-Box (STB), a Blu-ray disc (BD) player, a BD recorder, a DigitalVideo Disc (DVD) player, a High Definition (HD) DVD player, a DVDrecorder, a HD DVD recorder, a Personal Video Recorder (PVR), abroadcast HD receiver, a video source, an audio source, a video sink, anaudio sink, a stereo tuner, a broadcast radio receiver, a flat paneldisplay, a Personal Media Player (PMP), a digital video camera (DVC), adigital audio player, a speaker, an audio receiver, an audio amplifier,a gaming device, a data source, a data sink, a Digital Still camera(DSC), a media player, a Smartphone, a television, a music player, orthe like.

In some demonstrative aspects, device 102 may include, for example, oneor more of a processor 191, an input unit 192, an output unit 193, amemory unit 194, and/or a storage unit 195; and/or device 140 mayinclude, for example, one or more of a processor 181, an input unit 182,an output unit 183, a memory unit 184, and/or a storage unit 185.Devices 102 and/or 140 may optionally include other suitable hardwarecomponents and/or software components. In some demonstrative aspects,some or all of the components of one or more of devices 102 and/or 140may be enclosed in a common housing or packaging, and may beinterconnected or operably associated using one or more wired orwireless links. In other aspects, components of one or more of devices102 and/or 140 may be distributed among multiple or separate devices.

In some demonstrative aspects, processor 191 and/or processor 181 mayinclude, for example, a Central Processing Unit (CPU), a Digital SignalProcessor (DSP), one or more processor cores, a single-core processor, adual-core processor, a multiple-core processor, a microprocessor, a hostprocessor, a controller, a plurality of processors or controllers, achip, a microchip, one or more circuits, circuitry, a logic unit, anIntegrated Circuit (IC), an Application-Specific IC (ASIC), or any othersuitable multi-purpose or specific processor or controller. Processor191 may execute instructions, for example, of an Operating System (OS)of device 102 and/or of one or more suitable applications. Processor 181may execute instructions, for example, of an Operating System (OS) ofdevice 140 and/or of one or more suitable applications.

In some demonstrative aspects, input unit 192 and/or input unit 182 mayinclude, for example, a keyboard, a keypad, a mouse, a touch-screen, atouch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 193 and/or output unit 183may include, for example, a monitor, a screen, a touch-screen, a flatpanel display, a Light Emitting Diode (LED) display unit, a LiquidCrystal Display (LCD) display unit, a plasma display unit, one or moreaudio speakers or earphones, or other suitable output devices.

In some demonstrative aspects, memory unit 194 and/or memory unit 184includes, for example, a Random Access Memory (RAM), a Read Only Memory(ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flashmemory, a volatile memory, a non-volatile memory, a cache memory, abuffer, a short term memory unit, a long term memory unit, or othersuitable memory units. Storage unit 195 and/or storage unit 185 mayinclude, for example, a hard disk drive, a disk drive, a solid-statedrive (SSD), and/or other suitable removable or non-removable storageunits. Memory unit 194 and/or storage unit 195, for example, may storedata processed by device 102. Memory unit 184 and/or storage unit 185,for example, may store data processed by device 140.

In some demonstrative aspects, wireless communication devices 102 and/or140 may be capable of communicating content, data, information and/orsignals via a wireless medium (WM) 103. In some demonstrative aspects,wireless medium 103 may include, for example, a radio channel, an RFchannel, a WiFi channel, a cellular channel, a 5G channel, an IRchannel, a Bluetooth (BT) channel, a Global Navigation Satellite System(GNSS) Channel, and the like.

In some demonstrative aspects, WM 103 may include one or more wirelesscommunication frequency bands and/or channels. For example, WM 103 mayinclude one or more channels in a sub-10 Ghz wireless communicationfrequency band, for example, a 2.4 GHz wireless communication frequencyband, one or more channels in a 5 GHz wireless communication frequencyband, and/or one or more channels in a 6 GHz wireless communicationfrequency band. In another example, WM 103 may additionally oralternative include one or more channels in a mmWave wirelesscommunication frequency band.

In other aspects, WM 103 may include any other type of channel over anyother frequency band.

In some demonstrative aspects, device 102 and/or device 140 may includeone or more radios including circuitry and/or logic to perform wirelesscommunication between devices 102, 140 and/or one or more other wirelesscommunication devices. For example, device 102 may include one or moreradios 114, and/or device 140 may include one or more radios 144.

In some demonstrative aspects, radios 114 and/or 144 may include one ormore wireless receivers (Rx) including circuitry and/or logic to receivewireless communication signals, RF signals, frames, blocks, transmissionstreams, packets, messages, data items, and/or data. For example, aradio 114 may include at least one receiver 116, and/or a radio 144 mayinclude at least one receiver 146.

In some demonstrative aspects, radios 114 and/or 144 may include one ormore wireless transmitters (Tx) including circuitry and/or logic totransmit wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, a radio 114 may include at least one transmitter 118, and/or aradio 144 may include at least one transmitter 148.

In some demonstrative aspects, radios 114 and/or 144, transmitters 118and/or 148, and/or receivers 116 and/or 146 may include circuitry;logic; Radio Frequency (RF) elements, circuitry and/or logic; basebandelements, circuitry and/or logic; modulation elements, circuitry and/orlogic; demodulation elements, circuitry and/or logic; amplifiers; analogto digital and/or digital to analog converters; filters; and/or thelike. For example, radios 114 and/or 144 may include or may beimplemented as part of a wireless Network Interface Card (NIC), and thelike.

In some demonstrative aspects, radios 114 and/or 144 may be configuredto communicate over a 2.4 GHz band, a 5 GHz band, a 6 GHz band, and/orany other band, for example, a directional band, e.g., an mmWave band, a5G band, an S1G band, and/or any other band.

In some demonstrative aspects, radios 114 and/or 144 may include, or maybe associated with one or more antennas.

In some demonstrative aspects, device 102 may include one or moreantennas 107, and/or device 140 may include one or more antennas 147.

Antennas 107 and/or 147 may include any type of antennas suitable fortransmitting and/or receiving wireless communication signals, blocks,frames, transmission streams, packets, messages and/or data. Forexample, antennas 107 and/or 147 may include any suitable configuration,structure and/or arrangement of one or more antenna elements,components, units, assemblies and/or arrays. In some aspects, antennas107 and/or 147 may implement transmit and receive functionalities usingseparate transmit and receive antenna elements. In some aspects,antennas 107 and/or 147 may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements.

In some demonstrative aspects, device 102 may include a controller 124,and/or device 140 may include a controller 154. Controller 124 may beconfigured to perform and/or to trigger, cause, instruct and/or controldevice 102 to perform, one or more communications, to generate and/orcommunicate one or more messages and/or transmissions, and/or to performone or more functionalities, operations and/or procedures betweendevices 102, 140 and/or one or more other devices; and/or controller 154may be configured to perform, and/or to trigger, cause, instruct and/orcontrol device 140 to perform, one or more communications, to generateand/or communicate one or more messages and/or transmissions, and/or toperform one or more functionalities, operations and/or proceduresbetween devices 102, 140 and/or one or more other devices, e.g., asdescribed below.

In some demonstrative aspects, controllers 124 and/or 154 may include,or may be implemented, partially or entirely, by circuitry and/or logic,e.g., one or more processors including circuitry and/or logic, memorycircuitry and/or logic, Media-Access Control (MAC) circuitry and/orlogic, Physical Layer (PHY) circuitry and/or logic, baseband (BB)circuitry and/or logic, a BB processor, a BB memory, ApplicationProcessor (AP) circuitry and/or logic, an AP processor, an AP memory,and/or any other circuitry and/or logic, configured to perform thefunctionality of controllers 124 and/or 154, respectively. Additionallyor alternatively, one or more functionalities of controllers 124 and/or154 may be implemented by logic, which may be executed by a machineand/or one or more processors, e.g., as described below.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause, trigger and/or control a wireless device, e.g., device 102,and/or a wireless station, e.g., a wireless STA implemented by device102, to perform one or more operations, communications and/orfunctionalities, e.g., as described herein. In one example, controller124 may include at least one memory, e.g., coupled to the one or moreprocessors, which may be configured, for example, to store, e.g., atleast temporarily, at least some of the information processed by the oneor more processors and/or circuitry, and/or which may be configured tostore logic to be utilized by the processors and/or circuitry.

In one example, controller 154 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause, trigger and/or control a wireless device, e.g., device 140,and/or a wireless station, e.g., a wireless non-AP STA implemented bydevice 140, to perform one or more operations, communications and/orfunctionalities, e.g., as described herein. In one example, controller154 may include at least one memory, e.g., coupled to the one or moreprocessors, which may be configured, for example, to store, e.g., atleast temporarily, at least some of the information processed by the oneor more processors and/or circuitry, and/or which may be configured tostore logic to be utilized by the processors and/or circuitry.

In some demonstrative aspects, at least part of the functionality ofcontroller 124 may be implemented as part of one or more elements ofradio 114, and/or at least part of the functionality of controller 154may be implemented as part of one or more elements of radio 144.

In other aspects, the functionality of controller 124 may be implementedas part of any other element of device 102, and/or the functionality ofcontroller 154 may be implemented as part of any other element of device140.

In some demonstrative aspects, device 102 may include a messageprocessor 128 configured to generate, process and/or access one or moremessages communicated by device 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by device 102, and/or messageprocessor 128 may be configured to access and/or to process one or moremessages received by device 102, e.g., as described below.

In one example, message processor 128 may include at least one firstcomponent configured to generate a message, for example, in the form ofa frame, field, information element and/or protocol data unit, forexample, a MAC Protocol Data Unit (MPDU); at least one second componentconfigured to convert the message into a PHY Protocol Data Unit (PPDU),for example, by processing the message generated by the at least onefirst component, e.g., by encoding the message, modulating the messageand/or performing any other additional or alternative processing of themessage; and/or at least one third component configured to causetransmission of the message over a wireless communication medium, e.g.,over a wireless communication channel in a wireless communicationfrequency band, for example, by applying to one or more fields of thePPDU one or more transmit waveforms. In other aspects, message processor128 may be configured to perform any other additional or alternativefunctionality and/or may include any other additional or alternativecomponents to generate and/or process a message to be transmitted.

In some demonstrative aspects, device 140 may include a messageprocessor 158 configured to generate, process and/or access one or moremessages communicated by device 140.

In one example, message processor 158 may be configured to generate oneor more messages to be transmitted by device 140, and/or messageprocessor 158 may be configured to access and/or to process one or moremessages received by device 140, e.g., as described below.

In one example, message processor 158 may include at least one firstcomponent configured to generate a message, for example, in the form ofa frame, field, information element and/or protocol data unit, forexample, an MPDU; at least one second component configured to convertthe message into a PPDU, for example, by processing the messagegenerated by the at least one first component, e.g., by encoding themessage, modulating the message and/or performing any other additionalor alternative processing of the message; and/or at least one thirdcomponent configured to cause transmission of the message over awireless communication medium, e.g., over a wireless communicationchannel in a wireless communication frequency band, for example, byapplying to one or more fields of the PPDU one or more transmitwaveforms. In other aspects, message processor 158 may be configured toperform any other additional or alternative functionality and/or mayinclude any other additional or alternative components to generateand/or process a message to be transmitted.

In some demonstrative aspects, message processors 128 and/or 158 mayinclude, or may be implemented, partially or entirely, by circuitryand/or logic, e.g., one or more processors including circuitry and/orlogic, memory circuitry and/or logic, MAC circuitry and/or logic, PHYcircuitry and/or logic, BB circuitry and/or logic, a BB processor, a BBmemory, AP circuitry and/or logic, an AP processor, an AP memory, and/orany other circuitry and/or logic, configured to perform thefunctionality of message processors 128 and/or 158, respectively.Additionally or alternatively, one or more functionalities of messageprocessors 128 and/or 158 may be implemented by logic, which may beexecuted by a machine and/or one or more processors, e.g., as describedbelow.

In some demonstrative aspects, at least part of the functionality ofmessage processor 128 may be implemented as part of radio 114, and/or atleast part of the functionality of message processor 158 may beimplemented as part of radio 144.

In some demonstrative aspects, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124,and/or at least part of the functionality of message processor 158 maybe implemented as part of controller 154.

In other aspects, the functionality of message processor 128 may beimplemented as part of any other element of device 102, and/or thefunctionality of message processor 158 may be implemented as part of anyother element of device 140.

In some demonstrative aspects, at least part of the functionality ofcontroller 124 and/or message processor 128 may be implemented by anintegrated circuit, for example, a chip, e.g., a System on Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of one or more radios 114. For example, the chip or SoCmay include one or more elements of controller 124, one or more elementsof message processor 128, and/or one or more elements of one or moreradios 114. In one example, controller 124, message processor 128, andone or more radios 114 may be implemented as part of the chip or SoC.

In other aspects, controller 124, message processor 128 and/or the oneor more radios 114 may be implemented by one or more additional oralternative elements of device 102.

In some demonstrative aspects, at least part of the functionality ofcontroller 154 and/or message processor 158 may be implemented by anintegrated circuit, for example, a chip, e.g., a SoC. In one example,the chip or SoC may be configured to perform one or more functionalitiesof one or more radios 144. For example, the chip or SoC may include oneor more elements of controller 154, one or more elements of messageprocessor 158, and/or one or more elements of one or more radios 144. Inone example, controller 154, message processor 158, and one or moreradios 144 may be implemented as part of the chip or SoC.

In other aspects, controller 154, message processor 158 and/or one ormore radios 144 may be implemented by one or more additional oralternative elements of device 140.

In some demonstrative aspects, device 102 and/or device 140 may include,operate as, perform the role of, and/or perform one or morefunctionalities of, one or more STAs. For example, device 102 mayinclude at least one STA, and/or device 140 may include at least oneSTA.

In some demonstrative aspects, device 102 and/or device 140 may include,operate as, perform the role of, and/or perform one or morefunctionalities of, one or more Extremely High Throughput (EHT) STAs.For example, device 102 may include, operate as, perform the role of,and/or perform one or more functionalities of, one or more EHT STAs,and/or device 140 may include, operate as, perform the role of, and/orperform one or more functionalities of, one or more EHT STAs.

In other aspects, devices 102 and/or 140 may include, operate as,perform the role of, and/or perform one or more functionalities of, anyother wireless device and/or station, e.g., a WLAN STA, a WiFi STA, andthe like.

In some demonstrative aspects, device 102 and/or device 140 may beconfigured operate as, perform the role of, and/or perform one or morefunctionalities of, an access point (AP), e.g., an EHT AP STA.

In some demonstrative aspects, device 102 and/or device 140 may beconfigured to operate as, perform the role of, and/or perform one ormore functionalities of, a non-AP STA, e.g., an EHT non-AP STA.

In other aspects, device 102 and/or device 140 may operate as, performthe role of, and/or perform one or more functionalities of, any otheradditional or alternative device and/or station.

In one example, a station (STA) may include a logical entity that is asingly addressable instance of a medium access control (MAC) andphysical layer (PHY) interface to the wireless medium (WM). The STA mayperform any other additional or alternative functionality.

In one example, an AP may include an entity that contains one station(STA) and provides access to the distribution services, via the wirelessmedium (WM) for associated STAs. An AP may include a STA and adistribution system access function (DSAF).The AP may perform any otheradditional or alternative functionality.

In some demonstrative aspects devices 102 and/or 140 may be configuredto communicate in an EHT network, and/or any other network.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto operate in accordance with one or more Specifications, for example,including one or more IEEE 802.11 Specifications, e.g., an IEEE802.11-2020 Specification, an IEEE 802.11be Specification, and/or anyother specification and/or protocol.

In some demonstrative aspects, device 102 and/or device 140 may include,operate as, perform a role of, and/or perform the functionality of, oneor more multi-link logical entities, e.g., as described below.

In other aspect, device 102 and/or device 140 may include, operate as,perform a role of, and/or perform the functionality of, any otherentities, e.g., which are not multi-link logical entities.

For example, a multi-link logical entity may include a logical entitythat contains one or more STAs. The logical entity may have one MAC dataservice interface and primitives to the logical link control (LLC) and asingle address associated with the interface, which can be used tocommunicate on a distribution system medium (DSM). For example, the DSMmay include a medium or set of media used by a distribution system (DS)for communications between APs, mesh gates, and the portal of anextended service set (ESS). For example, the DS may include a systemused to interconnect a set of basic service sets (BSSs) and integratedlocal area networks (LANs) to create an extended service set (ESS). Inone example, a multi-link logical entity may allow STAs within themulti-link logical entity to have the same MAC address. The multi-linkentity may perform any other additional or alternative functionality.

In some demonstrative aspects, device 102 and/or device 140 may include,operate as, perform a role of, and/or perform the functionality of, aMulti-Link Device (MLD). For example, device 102 may include, operateas, perform a role of, and/or perform the functionality of, at least oneMLD, and/or device 140 may include, operate as, perform a role of,and/or perform the functionality of, at least one MLD, e.g., asdescribed below.

For example, an MLD may include a device that is a logical entity andhas more than one affiliated STA and has a single MAC service accesspoint (SAP) to LLC, which includes one MAC data service. The MLD mayperform any other additional or alternative functionality.

In some demonstrative aspects, for example, an infrastructure frameworkmay include a multi-link AP logical entity, which includes APs, e.g., onone side, and a multi-link non-AP logical entity, which includesnon-APs, e.g., on the other side.

In some demonstrative aspects, device 102 and/or device 140 may beconfigured to operate as, perform the role of, and/or perform one ormore functionalities of, an AP MLD.

In some demonstrative aspects, device 102 and/or device 140 may beconfigured to operate as, perform the role of, and/or perform one ormore functionalities of, a non-AP MLD.

In other aspects, device 102 and/or device 140 may operate as, performthe role of, and/or perform one or more functionalities of, any otheradditional or alternative device and/or station.

For example, an AP MLD may include an MLD, where each STA affiliatedwith the MLD is an AP. In one example, the AP MLD may include amulti-link logical entity, where each STA within the multi-link logicalentity is an EHT AP. The AP MLD may perform any other additional oralternative functionality.

For example, a non-AP MLD may include an MLD, where each STA affiliatedwith the MLD is a non-AP STA. In one example, the non-AP MLD may includea multi-link logical entity, where each STA within the multi-linklogical entity is a non-AP EHT STA. The non-AP MLD may perform any otheradditional or alternative functionality.

In one example, a multi-link infrastructure framework may be configuredas an extension from a one link operation between two STAs, e.g., an APand a non-AP STA.

In some demonstrative aspects, controller 124 may be configured tocause, trigger, instruct and/or control device 102 to operate as,perform a role of, and/or perform one or more operations and/orfunctionalities of, an AP MLD 131 including a plurality of AP STAs 133,e.g., including an AP STA 135, an AP STA 137 and/or an AP STA 139. Insome aspects, as shown in FIG. 1 , AP MLD 131 may include three AP STAs.In other aspects, AP MLD 131 may include any other number of AP STAs.

In one example, AP STA 135, AP STA 137 and/or AP STA 139 may operate as,perform a role of, and/or perform one or more operations and/orfunctionalities of, an EHT AP STA. In other aspects, AP STA 135, AP STA137 and/or AP STA 139 may perform any other additional or alternativefunctionality.

In some demonstrative aspects, for example, the one or more radios 114may include, for example, a radio for communication by AP STA 135 over afirst wireless communication frequency channel and/or frequency band,e.g., a 2.4 Ghz band, as described below.

In some demonstrative aspects, for example, the one or more radios 114may include, for example, a radio for communication by AP STA 137 over asecond wireless communication frequency channel and/or frequency band,e.g., a 5 Ghz band, as described below.

In some demonstrative aspects, for example, the one or more radios 114may include, for example, a radio for communication by AP STA 139 over athird wireless communication frequency channel and/or frequency band,e.g., a 6 Ghz band, as described below.

In some demonstrative aspects, the radios 114 utilized by APs 133 may beimplemented as separate radios. In other aspects, the radios 114utilized by APs 133 may be implemented by one or more shared and/orcommon radios and/or radio components.

In other aspects controller 124 may be configured to cause, trigger,instruct and/or control device 102 to operate as, perform a role of,and/or perform one or more operations and/or functionalities of, anyother additional or alternative entity and/or STA, e.g., a single STA,multiple STAs, and/or a non-MLD entity.

In some demonstrative aspects, controller 154 may be configured tocause, trigger, instruct and/or control device 140 to operate as,perform a role of, and/or perform one or more operations and/orfunctionalities of, an MLD 151 including a plurality of STAs 153, e.g.,including a STA 155, a STA 157 and/or a STA 159. In some aspects, asshown in FIG. 1 , MLD 151 may include three STAs. In other aspects, MLD151 may include any other number of STAs.

In one example, STA 155, STA 157 and/or STA 159 may operate as, performa role of, and/or perform one or more operations and/or functionalitiesof, an EHT STA. In other aspects, STA 155, STA 157 and/or STA 159 mayperform any other additional or alternative functionality.

In some demonstrative aspects, for example, the one or more radios 144may include, for example, a radio for communication by STA 155 over afirst wireless communication frequency channel and/or frequency band,e.g., a 2.4 Ghz band, as described below.

In some demonstrative aspects, for example, the one or more radios 144may include, for example, a radio for communication by STA 157 over asecond wireless communication frequency channel and/or frequency band,e.g., a 5 Ghz band, as described below.

In some demonstrative aspects, for example, the one or more radios 144may include, for example, a radio for communication by STA 159 over athird wireless communication frequency channel and/or frequency band,e.g., a 6 Ghz band, as described below.

In some demonstrative aspects, the radios 144 utilized by STAs 153 maybe implemented as separate radios. In other aspects, the radios 144utilized by STAs 153 may be implemented by one or more shared and/orcommon radios and/or radio components.

In some demonstrative aspects, controller 154 may be configured tocause, trigger, instruct and/or control MLD 151 to operate as, perform arole of, and/or perform one or more operations and/or functionalitiesof, a non-AP MLD. For example, STA 155, STA 157 and/or STA 159 mayoperate as, perform a role of, and/or perform one or more operationsand/or functionalities of, a non-AP EHT STA.

In some demonstrative aspects, controller 154 may be configured tocause, trigger, instruct and/or control MLD 151 to operate as, perform arole of, and/or perform one or more operations and/or functionalitiesof, an AP MLD. For example, STA 155, STA 157 and/or STA 159 may operateas, perform a role of, and/or perform one or more operations and/orfunctionalities of, an AP EHT STA.

In other aspects controller 154 may be configured to cause, trigger,instruct and/or control device 140 to operate as, perform a role of,and/or perform one or more operations and/or functionalities of, anyother additional or alternative entity and/or STA, e.g., a single STA,multiple STAs, and/or a non-MLD entity.

Reference is made to FIG. 2 , which schematically illustrates amulti-link communication scheme 200, which may be implemented inaccordance with some demonstrative aspects.

As shown in FIG. 2 , a first multi-link logical entity 202 (“multi-linklogical entity 1”), e.g., a first MLD, may include a plurality of STAs,e.g., including a STA 212, a STA 214, and a STA 216. In one example, APMLD 131 (FIG. 1 ) may perform one or more operations, one or morefunctionalities, the role of, and/or the functionality of, multi-linklogical entity 202.

As shown in FIG. 2 , a second multi-link logical entity 240 (“multi-linklogical entity 2”), e.g., a second MLD, may include a plurality of STAs,e.g., including a STA 252, a STA 254, and a STA 256. In one example, MLD151 (FIG. 1 ) may perform one or more operations, one or morefunctionalities, the role of, and/or the functionality of, multi-linklogical entity 240.

As shown in FIG. 2 , multi-link logical entity 202 and multi-linklogical entity 240 may be configured to form, setup and/or communicateover a plurality of links, for example, including a link 272 between STA212 and STA 252, a link 274 between STA 214 and STA 254, and/or a link276 between STA 216 and STA 256.

Reference is made to FIG. 3 , which schematically illustrates amulti-link communication scheme 300, which may be implemented inaccordance with some demonstrative aspects.

As shown in FIG. 3 , a multi-link AP logical entity 302, e.g., an APMLD, may include a plurality of AP STAs, e.g., including an AP STA 312,an AP STA 314, and an AP STA 316. In one example, AP MLD 131 (FIG. 1 )may perform one or more operations, one or more functionalities, therole of, and/or the functionality of, multi-link AP logical entity 302.

As shown in FIG. 3 , a multi-link non-AP logical entity 340, e.g., anon-AP MLD, may include a plurality of non-AP STAs, e.g., including anon-AP STA 352, a non-AP STA 354, and a non-AP STA 356. In one example,MLD 151 (FIG. 1 ) may perform one or more operations, one or morefunctionalities, the role of, and/or the functionality of, multi-linknon-AP logical entity 340.

As shown in FIG. 3 , multi-link AP logical entity 302 and multi-linknon-AP logical entity 340 may be configured to form, setup and/orcommunicate over a plurality of links, for example, including a link 372between AP STA 312 and non-AP STA 352, a link 374 between AP STA 314 andnon-AP STA 354, and/or a link 376 between AP STA 316 and non-AP STA 356.

For example, as shown in FIG. 3 , multi-link AP logical entity 302 mayinclude a multi-band AP MLD, which may be configured to communicate overa plurality of wireless communication frequency bands. For example, asshown in FIG. 3 , AP STA 312 may be configured to communicate over a 2.4Ghz frequency band, AP STA 314 may be configured to communicate over a 5Ghz frequency band, and/or AP STA 316 may be configured to communicateover a 6 Ghz frequency band. In other aspects, AP STA 312, AP STA 314,and/or AP STA 316, may be configured to communicate over any otheradditional or alternative wireless communication frequency bands.

Referring back to FIG. 1 , in some demonstrative aspects, devices 102and/or 140 may be configured to implement one or more mechanisms toprovide a technical solution to support wireless communication withimproved and/or reduced latency, e.g., as described below.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto implement one or more mechanisms to provide a technical solution tosupport improved cellular Quality of Service (QoS) management forwireless communication, e.g., as described below.

In some demonstrative aspects, reduced latency and/or QoS management maybe achieved, for example, by designing low-latency channel accessschemes, e.g., utilizing scheduling and/or any other mechanism.

For example, one or more schemes may be configured, e.g., in accordancewith an IEEE 802.11be Specification, for example, on top of multi-user(MU) scheduling mechanisms, e.g., in accordance with an IEEE 802.11axSpecification.

In one example, multi-link operations, e.g., according to an MLDarchitecture, may be implemented to provide a higher channel accessopportunity.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto implement one or more cellular QoS mechanisms to provide a technicalsolution to support improved cellular QoS management for wirelesscommunication, e.g., as described below.

For example, the cellular QoS mechanisms may be configured to provide atechnical solution to support efficient mapping between one or morecellular QoS parameters and one or more equivalent parameters.

In one example, a cellular QoS mechanism may be configured to supportefficient mapping of one or more 3GPP QoS parameters, e.g., which may becaptured in a 5G QoS characteristics element, for example, to one ormore equivalent Wi-Fi-specific QoS parameters. For example, the mappingbetween the cellular QoS parameters and the Wi-FI QoS parameters mayprovide a technical solution to support one or more QoS flows to beseamlessly moved between Wi-Fi networks and 3GPP networks, e.g., withoutsubstantially sacrificing performance.

In one example, the one or more 3GPP QoS parameters captured in the 5GQoS characteristics element may include one or more of the followingcharacteristics, for example, in accordance with a 3GPP specification:

TABLE 1 5G QoS Characteristic Description Resource Type Guaranteed BitRate (GBR), Delay-critical GBR or Non-GBR Priority Level Indicates apriority in scheduling resources among QoS Flows Packet Delay Budget(PDB) Defines an upper bound for the time that a packet may be delayedbetween the UE and the UPF that terminates the N6 interface Packet ErrorRate (PER) Defines an upper bound for the rate of PDUs, e.g. IP packets,that have been processed by the sender of a link layer protocol, e.g.,RLC in RAN of a 3GPP access, but that are not successfully delivered bythe corresponding receiver to the upper layer, e.g., PDCP in RAN of a3GPP access. Thus, the PER defines an upper bound for a rate ofnon-congestion related packet losses Averaging Window Represents theduration over which the bitrate, e.g., GFBR and MFBR, may be calculated.Maximum Data Burst Volume (MDBV) The largest amount of data that the5G-AN is required to serve within the period of the 5G-AN part of thePDB. GBR QoS Flows with Delay-critical Resource Type shall be associatedwith a MDBV. The MDBV aids the 5G-AN to enable low latency requirementsas whether a low latency can be achieved with a certain reliabilitydepends on packet size and inter-arrival rate of the packets

In other aspects, the one or more 3GPP QoS parameters captured in the 5GQoS characteristics element may include any other additional and/oralternative characteristics.

For example, the 3GPP QoS parameters may be conveyed from a core networkto an Access Network (AN), e.g., either explicitly or implicitly.

For example, the 3GPP QoS parameters may be provided, for example, usinga cellular QoS index (also referred to as a “fifth generation (5G) QoSIndex (5QI)”), which may be defined in a table of standardized 5G QoScharacteristics sets.

For example, a WiFi QoS signaling mechanism, e.g., which may beimplemented from Wi-Fi-6 onwards, may be based on Stream ClassificationService (SCS) mechanisms. For example, a STA may signal QoS parametersin an SCS request frame.

In one example, an SCS request frame for a traffic flow may includepacket classification parameters and a QoS characteristics element,which may include traffic characteristics information for the trafficflow.

For example, the one or more cellular QoS parameters may be mapped toone or more corresponding QoS characteristics, for example, to provide atechnical solution to maintain parity of QoS flows between 3GPP andWiFi.

For example, a mapping may be defined between the 3GPP parameters andthe Wi-Fi QoS characteristics, e.g., as follows:

TABLE 2 3GPP 5G QoS parameter Equivalent Wi-Fi QoSCharacteristics/parameter Resource Type (GBR/Non-GBR/Delay-critical GBR)May be converted as: Use Alternate queues with higher UP forGBR/Delay-Critical GBR flows; and/or lower UP for Non-GBR flows forAC_VO & AC_VI, to prioritize GBR flows over Non-GBR flows for AC_VO/VI.Delay-critical GBR - Set ‘drop eligible’ implying packets can be droppedafter delay bound is crossed. Priority Level Note: This may not be thesame as UP. The Priority level may be introduced as a new attribute forWi-Fi QoS to allow AP to prioritize among different flows Packet DelayBudget Map to “Delay Bound” in 802.11be QoS Characteristics element.Subtract 5G Core-Network-PDB before mapping per values defined in TS23.501 for different 5QIs. Packet Error Rate Map to “MSDU DeliveryRatio” in 802.11be QoS Characteristics. For example, PER may beconverted to MSDU Delivery Ratio per Table (3) below. Maximum Data BurstVolume Map to “Burst Size” in 802.11be QoS Characteristics element.Default Averaging Window May not be needed for Wi-Fi GBR/Delay-criticalGBR -GFBR Map to “Minimum Data Rate” in 802.11be QoS Characteristicselement. GBR/Delay-critical GBR -Avg (GFBR+MFBR) Map to “Mean Data Rate”in 802.11be QoS Characteristics element.

In other aspects, any other additional and/or alternative mapping may bedefined between one or more additional or alternative 3GPP parametersand one or more additional or alternative Wi-Fi QoS characteristics.

In one example, the packet error rate may be mapped to the “MSDUDelivery Ratio”, for example, according to the following table, e.g., asfollows:

TABLE 3 Value MSDU delivery ratio 0 Not specified 1 95% 2 96% 3 97% 498% 5 99% 6 99.9% 7 99.99% 8 99.999% 9 99.9999% 10-15 Reserved

In other aspects, any other additional and/or alterative mapping may beapplied between the packet error rate and the “MSDU Delivery Ratio”.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto implement a cellular QoS signaling mechanism, which may be configuredto provide a technical solution to support signaling of one or morecellular QoS parameters of a cellular QoS traffic flow, e.g., asdescribed below.

In some demonstrative aspects, the cellular QoS signaling mechanism maybe configured to provide a technical solution to support signaling ofone or more cellular QoS parameters, which may not have representationin a current version of a WiFi QoS characteristics element, e.g., asdescribed below.

In some demonstrative aspects, the cellular QoS signaling mechanism maybe configured to signal one or more cellular QoS parameters, e.g., of a5QI-related signaling, for example, in SCS request and/or SCS responseframes, e.g., as described below.

In some demonstrative aspects, the cellular QoS signaling mechanism maybe configured to enhance an SCS mechanism, e.g., in accordance with anIEEE 802.11be Specification, for example, to allow a STA to signal thecellular QoS parameters, e.g., as described below.

In some demonstrative aspects, the cellular QoS signaling mechanism maybe configured to support 5QI related signaling inside an SCS requestframe and/or an SCS response frame, e.g., as described below.

In some demonstrative aspects, an SCS request frame may be configured toinclude a QoS characteristics element, which may be configured toinclude additional information, e.g., the 5QI related signaling, forexample, to unambiguously signal one or more, e.g., some or all,parameters covered in 3GPP QoS characteristics, e.g., as describedbelow.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto perform one or more operations and/or communications to support thecellular QoS signaling mechanism based on a cellular QoS index, e.g., asdescribed below.

In some demonstrative aspects, an application and/or an OS, e.g.,executed by device 102 and/or device 140, may be configured to indicatean index, e.g., a cellular QoS index, of a standardized trafficcharacteristic, e.g., as described below.

In some demonstrative aspects, a STA and/or an AP, e.g., a STA and/or APimplemented by device 102 and/or device 140, may be configured tocommunicate to its peer STA/AP the cellular QoS index for a cellular QoStraffic flow, e.g., as described below.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto utilize the cellular QoS index, for example, to provide a technicalsolution to support a standardized way to map cellular QoScharacteristics, and/or to signal the cellular QoS characteristics in anetwork, e.g., as described below.

For example, devices 102 and/or 140 may be configured to implement thecellular QoS index to provide a technical solution to support bettercoexistence among different vendors, and/or to improve resourceallocation, e.g., scheduling, which, in turn, may enhance a QoSexperience for end-users.

For example, devices 102 and/or 140 may be configured to implement thecellular QoS index to provide a technical solution to support improvedinternetworking between cellular technologies, e.g., 5G/6G technologies,and WLAN technologies, e.g., WiFi technologies.

In one example, a STA may be connected to a cellular network, e.g., overa trusted or untrusted WLAN link. For example, standardized trafficcharacteristics corresponding to WLAN traffic characteristics of anapplication stream may be mapped to corresponding standardized cellularindexes, e.g., 5QI values. Accordingly, an element in the cellularnetwork, e.g., a 5G Core Network (5GC), may leverage the cellular QoSindex signaling, for example, to specify the cellular QoS requirementsfor those applications in the WLAN link.

For example, devices 102 and/or 140 may be configured to implement thecellular QoS index to provide a technical solution to support aconvenient mechanism for applications to signal cellular QoSinformation. For example, devices 102 and/or 140 may be configured toidentify a predefined setting of a set of a plurality of QoS parametersbased on the cellular QoS index, e.g., without having to go throughfilling out one or more specific fields.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto generate, process and/or communicate a cellular QoS index, the 5QI,e.g., as described below.

In some demonstrative aspects, the cellular QoS index may be configuredto indicate a predefined setting of a set of a plurality QoS parametersfor a cellular QoS traffic flow, e.g., as escribed below.

In some demonstrative aspects, the cellular QoS index may be defined,generated and/or provided by an application and/or an OS executed by adevice, e.g., device 102 and/or device 140, as described below.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto generate, process and/or communicate one or more frames and/ormessages based on a cellular QoS index, e.g., as described below.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto generate, process and/or communicate one or more frames and/ormessages including a cellular QoS index, e.g., as described below.

In some demonstrative aspects, devices 102 and/or 140 may be configuredto generate, process and/or communicate one or more frames and/ormessages including one or more information elements, which are based ona cellular QoS index, e.g., as described below.

In some demonstrative aspects, a plurality of predefined settings of aset of a plurality QoS parameters for a cellular QoS traffic flow, e.g.,corresponding to typical types and/or settings of traffic streams may bedefined, and may be known, e.g., a-priori, at some or all STAs. Forexample, the set of QoS traffic parameters may have an associated index,e.g., a 5QI.

In some demonstrative aspects, an AP, e.g., implemented by device 102,may be configured to receive and process a request for communication ofa cellular QoS traffic flow, e.g., including the 5QI.

In some demonstrative aspects, for example, based on receipt of the 5QI,the AP may determine a predefined setting from the plurality ofpredefined settings.

In some demonstrative aspects, device 102 and/or device 140 may beconfigured to generate, process and/or communicate one or more framesincluding a cellular QoS index, e.g., the 5QI, to signal cellular QoScharacteristics for a cellular QoS traffic flow, e.g., as describedbelow.

In some demonstrative aspects, a non-AP STA, e.g., a non-AP STAimplemented by device 140, may be configured to signal cellular QoSinformation to an AP, for example, in an SCS frame, for example, an SCSrequest frame, e.g., as described below.

For example, controller 154 may be configured to control a non-AP STAimplemented by device 140 to signal cellular QoS information to an APimplemented by device 102, for example, by including the cellular QoSindex in a frame, for example, an SCS frame, e.g., as described below.

In some demonstrative aspects, a STA, e.g., a non-AP STA implemented bydevice 140, may be configured to set a cellular QoS index value, e.g., a5QI value, in a cellular QoS index field, for example, a 5QI field,e.g., as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be configured to indicate a setting of a set of aplurality of cellular QoS parameters and/or characteristics, e.g., asdescribed below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be configured to indicate a setting of a set of aplurality of cellular QoS parameters and/or characteristics of acellular traffic stream to be communicated by the STA, e.g., asdescribed below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be configured to indicate a setting of a set of aplurality of cellular QoS parameters and/or characteristics of acellular traffic stream to be communicated between the STA and an AP,e.g., as described below.

In some demonstrative aspects, the cellular QoS index field may beincluded by a STA in a frame transmitted from the STA to an AP, forexample, to indicate a requested setting of a set of cellular QoSparameters and/or characteristics, which is requested by the STA, e.g.,as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be configured to indicate a predefined setting of the setof the plurality of QoS parameters and/or characteristics, e.g., asdescribed below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be configured to indicate a predefined setting of the setof QoS parameters and/or characteristics, for example, from a pluralityof predefined settings, e.g., as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be provided to the STA by an application and/or an OS,for example, according to one or more cellular QoS requirements, e.g.,as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be determined by the STA, for example, according to oneor more cellular QoS requirements, e.g., as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be selected from a plurality of predefined cellular QoSindex values, e.g., as described below.

In some demonstrative aspects, the cellular QoS index value, e.g., the5QI value, may be selected from the plurality of predefined cellular QoSindex values, for example, according to one or more cellular QoSrequirements and/or parameters, e.g., as described below.

In some demonstrative aspects, the plurality of predefined cellular QoSindex values may correspond to a respective plurality of predefinedsetting of cellular QoS parameters, e.g., as described below.

In some demonstrative aspects, the plurality of predefined cellular QoSindex values may correspond to a plurality of different types ofcellular traffic, e.g., as described below.

In some demonstrative aspects, the plurality of predefined cellular QoSindex values may correspond to a plurality of different types ofcellular QoS requirements, e.g., as described below.

In some demonstrative aspects, the plurality of predefined cellular QoSindex values may correspond to a plurality of different channelconditions, e.g., as described below.

In other aspects, some or all of the plurality of predefined cellularQoS index values may be defined based on any other additional oralternative criteria.

In some demonstrative aspects, a non-AP STA, e.g., the non-AP STAimplemented by device 140, may be configured to transmit a frameincluding a cellular QoS index field, e.g., as described below.

In some demonstrative aspects, the non-AP STA, e.g., the non-AP STAimplemented by device 140, may be configured to transmit the frameincluding the cellular QoS index field to an AP, e.g., an AP implementedby device 102.

In some demonstrative aspects, the non-AP STA, e.g., the non-AP STAimplemented by device 140, may be configured to transmit an SCS frameincluding the cellular QoS index field, e.g., as described below.

In some demonstrative aspects, the SCS frame may include an SCS requestframe, e.g., as described below.

In some demonstrative aspects, the cellular QoS index field may beincluded in any other additional or alternative type of frame.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause a non-AP STA implemented bydevice 140 to set a cellular QoS index value in a cellular QoS indexfield, for example, to indicate a predefined setting of a set of aplurality QoS parameters for a cellular QoS traffic flow to becommunicated by the non-AP STA over a WLAN, e.g., as described below.

In some demonstrative aspects, the set of the plurality QoS parametersmay include at least one of a resource type, a priority level, a PacketDelay Budget (PDB), a Packet Error Rate (PER), an averaging window,and/or a Maximum Data Burst Volume (MDBV), e.g., as described below.

In other aspects, the set of the plurality QoS parameters may includeany other additional and/or alternative parameters.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to transmit an SCS request to an AP of the WLAN, e.g., an APimplemented by device 102, e.g., as described below.

In some demonstrative aspects, the SCS request may include an SCSdescriptor element, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may includethe cellular QoS index field, e.g., as described below.

In other aspects, the cellular QoS index field may be included in anyother SCS descriptor element including any other additional oralternative fields, and/or having any other format.

In some demonstrative aspects, the cellular QoS index field may includea 5QI field, e.g., as described below.

In other aspects, the cellular QoS index field may include any othertype of field.

In some demonstrative aspects, the SCS descriptor element may include anelement ID field, a length field, e.g., after the element ID field, anSCS ID field, e.g., after the length field, and a request type field,e.g., after the SCSID field, e.g., as described below.

In some demonstrative aspects, the cellular QoS index field may be afterthe SCSID field, e.g., as described below.

In other aspects, the SCS descriptor element may include any otheradditional or alternative fields.

In other aspects, the cellular QoS index field may be implemented in anyother location in the SCS descriptor element.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause an AP implemented by device 102to process an SCS descriptor element in an SCS request from a non-APSTA, e.g., the SCS request from the non-AP STA implemented by device140, for example, to identify a cellular QoS index value in a cellularQoS index field in the SCS descriptor element, e.g., as described below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine, for example, based on the cellular QoS index value, apredefined setting of a set of the plurality QoS parameters for acellular QoS traffic flow to be communicated by the non-AP STA, e.g.,the non-AP STA implemented by device 140, over the WLAN, e.g., asdescribed below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to schedule one or more communications in the WLAN, for example,based on the predefined setting of the set of the plurality QoSparameters, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may include avendor specific element, e.g., as described below.

In some demonstrative aspects, the vendor specific element may includethe cellular QoS index field, e.g., as described below.

In some demonstrative aspects, the vendor specific element may include aresource type field, as described below.

In some demonstrative aspects, the resource type field may be configuredto indicate a resource type of the cellular QoS traffic flow, e.g., asdescribed below.

In some demonstrative aspects, the vendor specific element may include apriority field, e.g., as described below.

In some demonstrative aspects, the priority field may be configured toindicate a priority of the cellular QoS traffic flow, e.g., as describedbelow.

In some demonstrative aspects, the SCS descriptor element may include aQoS characteristics element, e.g., as described below.

In some demonstrative aspects, the QoS characteristics element mayinclude the cellular QoS index field, e.g., as described below.

In some demonstrative aspects, the QoS characteristics element mayinclude the resource type field, and/or the priority field, e.g., asdescribed below.

In some demonstrative aspects, the SCS descriptor element may includethe QoS characteristics element including a delay bound field, which maybe configured based on a Packet Delay Budget (PDB) of the cellular QoStraffic flow, e.g., as described below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set the delay bound field, for example, based on the PDBof the cellular QoS traffic flow, e.g., as described below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set a value in the delay bound field, for example, basedon a subtraction result of subtracting a Core Network PDB (CN-PDB) fromthe PDB of the cellular QoS traffic flow, e.g., as described below.

In some demonstrative aspects, the AP implemented by device 102 mayreceive the SCS descriptor element including the QoS characteristicselement including the delay bound field, e.g., as described below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine a PDB of the cellular QoS traffic flow, for example,based on the delay bound field in the QoS characteristics element in theSCS descriptor element, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may includethe QoS characteristics element including a MAC Service Data Unit(MSDU)delivery ratio field, which may be configured based on a PacketError Rate (PER) of the cellular QoS traffic flow, e.g., as describedbelow.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set the MSDU delivery ratio field in the QoScharacteristics element of the SCE descriptor element, for example,based on a PER of the cellular QoS traffic flow, e.g., as describedbelow.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 set a value in the MSDU delivery ratio field, for example,according to a predefined mapping table to map a plurality of predefinedPER values to a respective plurality of predefined MSDU delivery ratiovalues, e.g., as described below.

In one example, the predefined mapping table may be based on one or moreelements of Table 3. In other aspects, any other mapping table may beimplemented.

In some demonstrative aspects, the AP implemented by device 102 mayreceive the SCS descriptor element including the QoS characteristicselement including the MSDU delivery ratio field, e.g., as describedbelow.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine a PER of the cellular QoS traffic flow, for example,based on the MSDU delivery ratio field in the QoS characteristicselement in the SCS descriptor element, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may includethe QoS characteristics element including a minimum data rate field,which may be configured based on a Guaranteed Flow Bit Rate (GFBR) ofthe cellular QoS traffic flow, e.g., as described below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set the minimum data rate field in the QoS characteristicselement of the SCE descriptor element, for example, based on a GFBR ofthe cellular QoS traffic flow, e.g., as described below.

In some demonstrative aspects, the AP implemented by device 102 mayreceive the SCS descriptor element including the QoS characteristicselement including the minimum data rate field, e.g., as described below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine a GFBR of the cellular QoS traffic flow, for example,based on the minimum data rate field in the QoS characteristics elementin the SCS descriptor element, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may includethe QoS characteristics element including a mean data rate field, whichmay be configured based on an average of a GFBR and a Maximal Flow BitRate (MFBR) of the cellular QoS traffic flow, e.g., as described below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set the mean data rate field in the QoS characteristicselement of the SCE descriptor element, for example, based on an averageof the GFBR and the MFBR of the cellular QoS traffic flow, e.g., asdescribed below.

In some demonstrative aspects, the AP implemented by device 102 mayreceive the SCS descriptor element including the QoS characteristicselement including the mean data rate field, e.g., as described below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine a GFBR of the cellular QoS traffic flow, for example,based on the minimum data rate field in the QoS characteristics elementin the SCS descriptor element, e.g., as described below.

In some demonstrative aspects, the SCS descriptor element may include aresource type field, e.g., as described below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set a resource type field in the SCS descriptor element toindicate a resource type of the cellular QoS traffic flow, e.g., asdescribed below.

In some demonstrative aspects, controller 154 may be configured tocontrol, trigger, instruct, and/or cause the non-AP STA implemented bydevice 140 to set the resource type field to a value from a plurality ofpredefined resource type field values, e.g., as described below.

In some demonstrative aspects, the plurality of predefined resource typefield values may include, for example, a first resource type field valueto indicate a GBR flow, a second resource type field value to indicate anon-GBR flow, and/or a third resource type field value to indicate aGBR-delay critical flow, e.g., as described below.

In other aspects, the plurality of predefined resource type field valuesmay include any other additional and/or alternative values.

In some demonstrative aspects, the AP implemented by device 102 mayreceive the SCS descriptor including the resource type field, e.g., asdescribed below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine a resource type of the cellular QoS traffic flow, forexample, based on the resource type field in the SCS descriptor element,e.g., as described below.

In some demonstrative aspects, controller 124 may be configured tocontrol, trigger, instruct, and/or cause the AP implemented by device102 to determine the resource type of the cellular QoS traffic flow, forexample, based on the value from the plurality of predefined resourcetype field values, e.g., as described below.

Reference is made to FIG. 4 , which schematically illustrates an SCSdescriptor element 400, in accordance with some demonstrative aspects.For example, device 102 (FIG. 1 ) and/or device 140 (FIG. 1 ) may beconfigured to generate, process and/or communicate one or more framesand/or messages including the SCS descriptor element 400.

In some demonstrative aspects, the SCS descriptor element 400 may becommunicated in an SCS setup request frame, for example, to support thecellular QoS signaling mechanism.

In some demonstrative aspects, the SCS setup request frame may becommunicated in a WLAN between a non-AP STA, e.g., implemented by device140 (FIG. 1 ), and an AP of the WLAN, e.g., implemented by device 102(FIG. 1 ).

In some demonstrative aspects, the SCS descriptor element 400 mayinclude a cellular QoS index field 456, e.g., a 5QI field 456, toindicate a predefined setting of a set of a plurality QoS parameters fora cellular QoS traffic flow to be communicated by the non-AP STA overthe WLAN.

In some demonstrative aspects, as shown in FIG. 4 , the SCS descriptorelement 400 may include a vendor specific element 424 including the 5QIfield 456.

In some demonstrative aspects, as shown in FIG. 4 , vendor specificelement 424 may include a resource type field 452 (“Resources Type”)configured to indicate a resource type of the cellular QoS traffic flow.

In some demonstrative aspects, as shown in FIG. 4 , vendor specificelement 424 may include a priority field 454 (“Priority Level”)configured to indicate a priority of the cellular QoS traffic flow.

In some demonstrative aspects, as shown in FIG. 4 , the SCS descriptorelement 400 may include an element ID field 410, a length field 412after the element ID field 410, an SCSID field 414 after the lengthfield 412, a request type field 416 after the SCSID field 414, and oneor more predefined parameter elements and/or fields 418 after therequest type field 416.

In some demonstrative aspects, as shown in FIG. 4 , the vendor specificelement 424 may be after the SCSID field 414.

In some demonstrative aspects, as shown in FIG. 4 , the SCS descriptorelement 400 may include one or more optional/reserved subelements 426,e.g., after the vendor specific element 424.

In some demonstrative aspects, a non-AP STA, e.g., implemented by device140 (FIG. 1 ), may be configured to set a cellular QoS index value in5QI field 456, for example, to indicate the predefined setting of theset of the plurality QoS parameters for the cellular QoS traffic flow,e.g., as described above.

In some demonstrative aspects, an AP, e.g., implemented by device 102(FIG. 1 ), may be configured to determine, based on the cellular QoSindex value in 5QI field 456, the predefined setting of the set of theplurality QoS parameters to schedule one or more communications in theWLAN, based on the predefined setting of the set of the plurality QoSparameters, e.g., as described above.

In some demonstrative aspects, as shown in FIG. 4 , the SCS descriptorelement 400 may include one or more QoS characteristics elements 420,e.g., an optional QoS characteristics element, for example, after theone or more predefined parameter elements and/or fields 418.

In some demonstrative aspects, a cellular QoS index field, e.g., a 5QIfield, may be implemented as part of a QoS characteristics element,e.g., a QoS characteristics element 420, for example, instead of, or inaddition to, 5QI field 456 in the vendor specific element 424, e.g., asdescribed below.

Reference is made to FIG. 5 , which schematically illustrates a QoScharacteristics element 500, in accordance with some demonstrativeaspects. For example, device 102 (FIG. 1 ) and/or device 140 (FIG. 1 )may be configured to generate, process and/or communicate one or moreframes and/or messages including QoS characteristics element 500.

In some demonstrative aspects, QoS characteristics elements 420 (FIG. 4) may include a QoS characteristics element 500.

In some demonstrative aspects, QoS characteristics element 500 mayinclude information, which may be configured to support and/or may berequired to support, setting of one or more, e.g., a plurality of,cellular QoS parameters for a cellular QoS traffic flow.

In some demonstrative aspects, QoS characteristics element 500 may becommunicated in an SCS descriptor element, e.g., SCS descriptor element400 (FIG. 4 ) in an SCS setup request frame, for example, to support thecellular QoS signaling mechanism.

In some demonstrative aspects, the SCS setup request frame may becommunicated in a WLAN between a non-AP STA, e.g., implemented by device140 (FIG. 1 ), and an AP of the WLAN, e.g., implemented by device 102(FIG. 1 ).

In some demonstrative aspects, as shown in FIG. 5 , QoS characteristicselement 500 may include a cellular QoS index field 556, e.g., a 5QIfield 556, to indicate a predefined setting of a set of a plurality QoSparameters for a cellular QoS traffic flow to be communicated by thenon-AP STA over the WLAN.

In some demonstrative aspects, as shown in FIG. 5 , QoS characteristicselement 500 may include a resource type field 552 (“Resources Type”)configured to indicate a resource type of the cellular QoS traffic flow.

For example, resource type field 552 may be set to a value from aplurality of predefined resource type field values, which may include,for example, a first resource type field value to indicate a GuaranteedBit Rate (GBR) flow, a second resource type field value to indicate anon-GBR flow, and/or a third resource type field value to indicate aGBR-delay critical flow, e.g., as described above.

In some demonstrative aspects, as shown in FIG. 5 , QoS characteristicselement 500 may include a priority field 554 (“Priority Level”)configured to indicate a priority of the cellular QoS traffic flow.

In one example, a priority level value in the priority field 554 mayindicate a relative priority among different DL flows, for example, fromone or more different non-AP STAs, at the AP.

In some demonstrative aspects, as shown in FIG. 5 , the QoScharacteristics element 500 may include a delay bound field 502, whichmay be set, for example, to indicate a Packet Delay Budget (PDB) of thecellular QoS traffic flow, e.g., as described above.

In some demonstrative aspects, as shown in FIG. 5 , the QoScharacteristics element 500 may include an MSDU delivery ratio field544, which may be set, for example, to indicate a Packet Error Rate(PER) of the cellular QoS traffic flow, e.g., as described above.

For example, MSDU delivery ratio field 544 may be set to a valueaccording to a predefined mapping table configured to map a plurality ofpredefined PER values to a respective plurality of predefined MSDUdelivery ratio values, e.g., as described above.

In some demonstrative aspects, as shown in FIG. 5 , the QoScharacteristics element 500 may include a minimum data rate field 526,which may be set to indicate a Guaranteed Flow Bit Rate (GFBR) of thecellular QoS traffic flow, e.g., as described above.

In some demonstrative aspects, as shown in FIG. 5 , the QoScharacteristics element 500 may include a mean data rate field 536,which may be set to indicate an average of a GFBR and a Maximal Flow BitRate (MFBR) of the cellular QoS traffic flow, e.g., as described above.

In some demonstrative aspects, a non-AP STA, e.g., implemented by device140 (FIG. 1 ), may be configured to set a cellular QoS index value in5QI field 556, for example, to indicate the predefined setting of theset of the plurality QoS parameters for the cellular QoS traffic flow,e.g., as described above.

In some demonstrative aspects, an AP, e.g., implemented by device 102(FIG. 1 ), may be configured to determine, based on the cellular QoSindex value in 5QI field 556, the predefined setting of the set of theplurality QoS parameters to schedule one or more communications in theWLAN, based on the predefined setting of the set of the plurality QoSparameters corresponding to the 5QI value in the 5QI field 556, e.g., asdescribed above.

In some demonstrative aspects, as shown in FIG. 5 , QoS Characteristicselement may include one or more newly additional fields, e.g., resourcetype field 552, 5QI field 556, and/or priority level field 554.

In some demonstrative aspects, presence of the additional fields may besignaled, for example, using a reserved bit in a Presence Bitmap ofAdditional Parameters, e.g., in a control info field 525 in the QoScharacteristics element 500.

In some demonstrative aspects, a 5QI value may be explicitly signaled inan SCS descriptor element, e.g., SCS descriptor element 400 (FIG. 4 ).In one example, the 5QI value may be signaled inside a new field in aQoS Characteristics element, e.g., 5QI field 556 in QoS characteristicselement 500. In one example, the 5QI value may be signaled inside a newfield in the SCS descriptor element, e.g., 5QI field 456 (FIG. 4 ) inthe SCS descriptor element 400 (FIG. 4 ), as described above.

In some demonstrative aspects, one or more of parameters correspondingto the 5QI value, e.g., a delay bound value or the like, in the SCSdescriptor element, e.g., in the QoS characteristics element 500included in the SCS descriptor element 400 (FIG. 4 ), may be reserved ornot present, for example, if the parameters corresponding to the 5QIvalue are the default values.

In some demonstrative aspects, one or more parameters corresponding tothe 5QI value, e.g., a delay bound value or the like, in the SCSdescriptor element, e.g., in the QoS characteristics element 500included in the SCS descriptor element 400 (FIG. 4 ), may be set tonon-reserved values, or may be present, for example, to signalnon-default values, for example, if the parameters corresponding to the5QI value are not the default values.

In some demonstrative aspects, a non-AP STA, e.g., implemented by device140 (FIG. 2 ), may utilize a field, e.g., a new field, to signal whetheror not one or more default parameters associated with the 5QI value arepresent.

In some demonstrative aspects, a resource type parameter value in aresource type field, e.g., resource type field 552 and/or resource typefield 452 (FIG. 4 ), may be encoded, for example, according to one ormore, e.g., some or all, of the definitions in the following table:

TABLE 4 Resources Type field value Interpretation 0 (GBR) Packets forthis flow should be prioritized over other flows and should not bedropped. The packets crossing the latency bound should not be count aslost. 1 (non-GBR) This flow is less prioritized than GBR. 2 (GBR-delaycritical) This flow should be prioritized over non-GBR flows and may bedropped if the experienced latency crosses the delay bound. The packetscrossing the latency bound should be considered as lost and counttowards PER. 3-255 Reserved.

In other aspects, the resource type field may include, and/or may beencoded using, any other additional and/or alternative values.

In some demonstrative aspects, information in the resource type field,e.g., resource type field 552 and/or resource type field 452 (FIG. 4 ),may be included, e.g., partially contained, in an Intra-Access Priorityelement. For example, the Intra-Access Priority element may be signaledwith an SCS descriptor element, e.g., SCS descriptor element 400 (FIG. 4), for example, with the same SCS descriptor element, which includes theresource type field 552 and/or resource type field 452 (FIG. 4 ).

In one example, the Intra-Access Priority element to signal the resourcetype parameter value, e.g., as follows:

-   Alternate Queue set to 0 - to signal non-GBR flow.-   Alternate Queue set to 1 and Drop Eligibility set to 0 - to signal    GBR flow.-   Alternate Queue set to 1 and Drop Eligibility set to 1 - to signal    Delay-critical GBR flow.

In some demonstrative aspects, an SCS descriptor element, e.g., SCSdescriptor element 400 (FIG. 4 ), including a QoS characteristicselement, e.g., QoS characteristics element 500, may include a newsubelement, e.g., a vendor specific element or a 5G-QoS specificelement.

In some demonstrative aspects, the new subelement, e.g., which may beincluded in vendor specific element 424 (FIG. 4 ), may include one ormore cellular QoS parameters, which are not included in the QoScharacteristics element, e.g., QoS characteristics element 500. Forexample, the new subelement may include one or more cellular QoSparameters, for example, a resource type value, a priority level, and/ora 5QI index value, e.g., as described above.

In some demonstrative aspects, an overall QoS characteristics for thecellular QoS traffic flow may be signaled, for example, by setting thenew subelement, e.g., subelements 452, 454 and/or 456 (FIG. 4 ), alongwith the QoS characteristics element, e.g., QoS characteristics element500, in a same SCS descriptor element, e.g., SCS descriptor element 400(FIG. 4 ).

In some demonstrative aspects, interpretation of one or more fields inthe QoS characteristics element, e.g., QoS characteristics element 500,may be determined and/or changed, for example, when the SCS descriptorelement containing the QoS characteristics element, e.g., SCS descriptorelement 400 (FIG. 4 ), includes one or more parameters, e.g., in thesubelements 452, 454 and/or 456 (FIG. 4 ), corresponding to the cellularQoS traffic flow, e.g., a 3GPP QoS flow.

In one example, one or more fields in the QoS characteristics elementmay be interpreted as follows, for example, when the SCS descriptorelement containing the QoS characteristics element, e.g., SCS descriptorelement 400 (FIG. 4 ), includes one or more parameters, e.g., in thesubelements 452, 454 and/or 456 (FIG. 4 ):

-   A minimum service interval field, e.g., Minimum Service Interval    field 522, may be reserved or set to unspecified value.-   A maximum service interval field, e.g., Maximum Service Interval    field 521, may be reserved or set to unspecified value.-   A minimum data rate field, e.g., Minimum Data Rate field 526, may be    reserved or set to unspecified value.

Reference is made to FIG. 6 , which schematically illustrates a methodof communicating a cellular QoS index, in accordance with somedemonstrative aspects. For example, one or more of the operations of themethod of FIG. 6 may be performed by one or more elements of a system,e.g., system 100 (FIG. 1 ), for example, one or more wireless devices,e.g., device 102 (FIG. 1 ), device 140 (FIG. 1 ), a controller, e.g.,controller 124 (FIG. 1 ) and/or controller 154 (FIG. 1 ), a radio, e.g.,radio 114 (FIG. 1 ) and/or radio 144 (FIG. 1 ), and/or a messageprocessor, e.g., message processor 128 (FIG. 1 ) and/or messageprocessor 158 (FIG. 1 ).

As indicated at block 602, the method may include setting, at a non-APSTA, a cellular QoS index value in a cellular QoS index field toindicate a predefined setting of a set of a plurality QoS parameters fora cellular QoS traffic flow to be communicated by the non-AP STA over aWLAN. For example, controller 154 (FIG. 1 ) may be configured to causethe non-AP STA implemented by device 140 (FIG. 1 ) to set the cellularQoS index value, e.g., the 5QI value, in the cellular QoS index field toindicate the predefined setting of the set of the plurality QoSparameters for the cellular QoS traffic flow to be communicated by thenon-AP STA implemented by device 140 (FIG. 1 ) over the WLAN, e.g., asdescribed above.

As indicated at block 604, the method may include transmitting an SCSrequest from the non-AP STA to an AP of the WLAN, the SCS requestincluding an SCS descriptor element including the cellular QoS index.For example, controller 154 (FIG. 1 ) may be configured to cause thenon-AP STA implemented by device 140 (FIG. 1 ) to transmit the SCSrequest to the AP, e.g., implemented by device 102 (FIG. 1 ), e.g., asdescribed above.

Reference is made to FIG. 7 , which schematically illustrates a methodof communicating a cellular QoS index, in accordance with somedemonstrative aspects. For example, one or more of the operations of themethod of FIG. 7 may be performed by one or more elements of a system,e.g., system 100 (FIG. 1 ), for example, one or more wireless devices,e.g., device 102 (FIG. 1 ), device 140 (FIG. 1 ), a controller, e.g.,controller 124 (FIG. 1 ) and/or controller 154 (FIG. 1 ), a radio, e.g.,radio 114 (FIG. 1 ) and/or radio 144 (FIG. 1 ), and/or a messageprocessor, e.g., message processor 128 (FIG. 1 ) and/or messageprocessor 158 (FIG. 1 ).

As indicated at block 702, the method may include processing at an AP anSCS descriptor element in an SCS request from a non-AP STA to identify acellular QoS index value in a cellular QoS index field in the SCSdescriptor element. For example, controller 124 (FIG. 1 ) may beconfigured to cause the AP implemented by device 102 (FIG. 1 ) toprocess the SCS descriptor element in the SCS request from the non-APSTA, e.g., implemented by device 140 (FIG. 1 ), to identify the cellularQoS index value in the cellular QoS index field in the SCS descriptorelement, e.g., as described above.

As indicated at block 704, the method may include determining, based onthe cellular QoS index value, a predefined setting of a set of aplurality QoS parameters for a cellular QoS traffic flow to becommunicated by the non-AP STA over the WLAN. For example, controller124 (FIG. 1 ) may be configured to cause the AP implemented by device102 (FIG. 1 ) to determine, based on the cellular QoS index value, thepredefined setting of the set of the plurality QoS parameters for thecellular QoS traffic flow to be communicated by the non-AP STA, e.g.,implemented by device 140 (FIG. 1 ), over the WLAN, e.g., as describedabove.

As indicated at block 706, the method may include scheduling one or morecommunications in the WLAN based on the predefined setting of the set ofthe plurality QoS parameters. For example, controller 124 (FIG. 1 ) maybe configured to cause the AP implemented by device 102 (FIG. 1 ) toschedule one or more communications in the WLAN based on the predefinedsetting of the set of the plurality QoS parameters, e.g., as describedabove.

Reference is made to FIG. 8 , which schematically illustrates a productof manufacture 800, in accordance with some demonstrative aspects.Product 800 may include one or more tangible computer-readable(“machine-readable”) non-transitory storage media 802, which may includecomputer-executable instructions, e.g., implemented by logic 804,operable to, when executed by at least one computer processor, enablethe at least one computer processor to implement one or more operationsat device 102 (FIG. 1 ), device 140 (FIG. 1 ), MLD 131 (FIG. 1 ), MLD151 (FIG. 1 ), radio 114 (FIG. 1 ), radio 144 (FIG. 1 ), transmitter 118(FIG. 1 ), transmitter 148 (FIG. 1 ), receiver 116 (FIG. 1 ), receiver146 (FIG. 1 ), message processor 128 (FIG. 1 ), message processor 158(FIG. 1 ), controller 124 (FIG. 1 ), and/or controller 154 (FIG. 1 ), tocause device 102 (FIG. 1 ), device 140 (FIG. 1 ), MLD 131 (FIG. 1 ), MLD151 (FIG. 1 ), radio 114 (FIG. 1 ), radio 144 (FIG. 1 ), transmitter 118(FIG. 1 ), transmitter 148 (FIG. 1 ), receiver 116 (FIG. 1 ), receiver146 (FIG. 1 ), message processor 128 (FIG. 1 ), message processor 158(FIG. 1 ), controller 124 (FIG. 1 ), and/or controller 154 (FIG. 1 ), toperform, trigger and/or implement one or more operations and/orfunctionalities, and/or to perform, trigger and/or implement one or moreoperations and/or functionalities described with reference to the FIGS.1-7 , and/or one or more operations described herein. The phrases“non-transitory machine-readable medium” and “computer-readablenon-transitory storage media” may be directed to include all machineand/or computer readable media, with the sole exception being atransitory propagating signal.

In some demonstrative aspects, product 800 and/or machine-readablestorage media 802 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage media 802 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), flash memory (e.g., NOR or NANDflash memory), content addressable memory (CAM), polymer memory,phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a harddrive, and the like. The computer-readable storage media may include anysuitable media involved with downloading or transferring a computerprogram from a remote computer to a requesting computer carried by datasignals embodied in a carrier wave or other propagation medium through acommunication link, e.g., a modem, radio or network connection.

In some demonstrative aspects, logic 804 may include instructions, data,and/or code, which, if executed by a machine, may cause the machine toperform a method, process and/or operations as described herein. Themachine may include, for example, any suitable processing platform,computing platform, computing device, processing device, computingsystem, processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware, software,firmware, and the like.

In some demonstrative aspects, logic 804 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, machine code, and the like.

EXAMPLES

The following examples pertain to further aspects.

Example 1 includes an apparatus comprising logic and circuitryconfigured to cause a wireless communication station (STA), e.g., a nonAccess Point (AP) (non-AP) STA, to set a cellular Quality of Service(QoS) index value in a cellular QoS index field to indicate a predefinedsetting of a set of a plurality QoS parameters for a cellular QoStraffic flow to be communicated by the non-AP STA over a Wireless LocalArea Network (WLAN); and transmit a Stream Classification Service (SCS)request to an Access Point (AP) of the WLAN, the SCS request comprisingan SCS descriptor element, the SCS descriptor element comprising thecellular QoS index field.

Example 2 includes the subject matter of Example 1, and optionally,wherein the SCS descriptor element comprises a vendor specific element,the vendor specific element comprising the cellular QoS index field.

Example 3 includes the subject matter of Example 2, and optionally,wherein the vendor specific element comprises at least one of a resourcetype field, or a priority field, wherein the resource type field isconfigured to indicate a resource type of the cellular QoS traffic flow,wherein the priority field is configured to indicate a priority of thecellular QoS traffic flow.

Example 4 includes the subject matter of Example 1, and optionally,wherein the SCS descriptor element comprises a QoS characteristicselement, the QoS characteristics element comprising the cellular QoSindex field.

Example 5 includes the subject matter of Example 4, and optionally,wherein QoS characteristics element comprises at least one of a resourcetype field, or a priority field, wherein the resource type field isconfigured to indicate a resource type of the cellular QoS traffic flow,wherein the priority field is configured to indicate a priority of thecellular QoS traffic flow.

Example 6 includes the subject matter of any one of Examples 1-5, andoptionally, wherein the apparatus is configured to cause the non-AP STAto set a delay bound field based on a Packet Delay Budget (PDB) of thecellular QoS traffic flow, wherein the SCS descriptor element comprisesa QoS characteristics element, the QoS characteristics elementcomprising the delay bound field.

Example 7 includes the subject matter of Example 6, and optionally,wherein the apparatus is configured to cause the non-AP STA to set avalue in the delay bound field based on a subtraction result ofsubtracting a Core Network PDB (CN-PDB) from the PDB of the cellular QoStraffic flow.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, wherein the apparatus is configured to cause the non-AP STAto set a Medium Access Control (MAC) Service Data Unit (MSDU) deliveryratio field based on a Packet Error Rate (PER) of the cellular QoStraffic flow, wherein the SCS descriptor element comprises a QoScharacteristics element, the QoS characteristics element comprising theMSDU delivery ratio field.

Example 9 includes the subject matter of Example 8, and optionally,wherein the apparatus is configured to cause the non-AP STA to set avalue in the MSDU delivery ratio field according to a predefined mappingtable, the mapping table configured to map a plurality of predefined PERvalues to a respective plurality of predefined MSDU delivery ratiovalues.

Example 10 includes the subject matter of any one of Examples 1-9, andoptionally, wherein the apparatus is configured to cause the non-AP STAto set a minimum data rate field based on a Guaranteed Flow Bit Rate(GFBR) of the cellular QoS traffic flow, wherein the SCS descriptorelement comprises a QoS characteristics element, the QoS characteristicselement comprising the minimum data rate field.

Example 11 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the apparatus is configured to cause the non-AP STAto set a mean data rate field based on an average of a Guaranteed FlowBit Rate (GFBR) and a Maximal Flow Bit Rate (MFBR) of the cellular QoStraffic flow, wherein the SCS descriptor element comprises a QoScharacteristics element, the QoS characteristics element comprising themean data rate field.

Example 12 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the apparatus is configured to cause the non-AP STAto set a resource type field in the SCS descriptor element to indicate aresource type of the cellular QoS traffic flow.

Example 13 includes the subject matter of Example 12, and optionally,wherein the apparatus is configured to cause the non-AP STA to set theresource type field to a value from a plurality of predefined resourcetype field values, the plurality of predefined resource type fieldvalues comprising a first resource type field value to indicate aGuaranteed Bit Rate (GBR) flow, a second resource type field value toindicate a non-GBR flow, and a third resource type field value toindicate a GBR-delay critical flow.

Example 14 includes the subject matter of any one of Examples 1-13, andoptionally, wherein the set of the plurality QoS parameters comprises atleast one of a resource type, a priority level, a Packet Delay Budget(PDB), a Packet Error Rate (PER), an averaging window, or a Maximum DataBurst Volume (MDBV).

Example 15 includes the subject matter of any one of Examples 1-14, andoptionally, wherein the SCS descriptor element comprises an elementidentifier (ID) field, a length field after the element ID field, an SCSID field after the length field, and a request type field after theSCSID field, wherein the cellular QoS index field is after the SCSIDfield.

Example 16 includes the subject matter of any one of Examples 1-15, andoptionally, wherein the cellular QoS index field comprises a fifthgeneration (5G) QoS Index (5QI) field.

Example 17 includes the subject matter of any one of Examples 1-16, andoptionally, comprising a radio to transmit the SCS request.

Example 18 includes the subject matter of Example 17, and optionally,comprising one or more antennas connected to the radio, and a processorto execute instructions of an operating system of the non-AP STA.

Example 19 includes an apparatus comprising logic and circuitryconfigured to cause an Access Point (AP) of a Wireless Local AreaNetwork (WLAN) to process a Stream Classification Service (SCS)descriptor element in an SCS request from a non-AP wirelesscommunication station (STA) to identify a cellular Quality of Service(QoS) index value in a cellular QoS index field in the SCS descriptorelement; determine, based on the cellular QoS index value, a predefinedsetting of a set of a plurality QoS parameters for a cellular QoStraffic flow to be communicated by the non-AP STA over the WLAN; andschedule one or more communications in the WLAN based on the predefinedsetting of the set of the plurality QoS parameters.

Example 20 includes the subject matter of Example 19, and optionally,wherein the SCS descriptor element comprises a vendor specific element,the vendor specific element comprising the cellular QoS index field.

Example 21 includes the subject matter of Example 20, and optionally,wherein the vendor specific element comprises at least one of a resourcetype field, or a priority field, wherein the resource type field isconfigured to indicate a resource type of the cellular QoS traffic flow,wherein the priority field is configured to indicate a priority of thecellular QoS traffic flow.

Example 22 includes the subject matter of Example 19, and optionally,wherein the SCS descriptor element comprises a QoS characteristicselement, the QoS characteristics element comprising the cellular QoSindex field.

Example 23 includes the subject matter of Example 22, and optionally,wherein QoS characteristics element comprises at least one of a resourcetype field, or a priority field, wherein the resource type field isconfigured to indicate a resource type of the cellular QoS traffic flow,wherein the priority field is configured to indicate a priority of thecellular QoS traffic flow.

Example 24 includes the subject matter of any one of Examples 19-23, andoptionally, wherein the apparatus is configured to cause the AP todetermine a Packet Delay Budget (PDB) of the cellular QoS traffic flowbased on a delay bound field in a QoS characteristics element in the SCSdescriptor element.

Example 25 includes the subject matter of Example 24, and optionally,wherein a value in the delay bound field is based on a subtractionresult of subtracting a Core Network PDB (CN-PDB) from the PDB of thecellular QoS traffic flow.

Example 26 includes the subject matter of any one of Examples 19-25, andoptionally, wherein the apparatus is configured to cause the AP todetermine a Packet Error Rate (PER) of the cellular QoS traffic flowbased on a Medium Access Control (MAC) Service Data Unit (MSDU) deliveryratio field in a QoS characteristics element in the SCS descriptorelement.

Example 27 includes the subject matter of Example 26, and optionally,wherein a value in the MSDU delivery ratio field is based on apredefined mapping table, the mapping table configured to map aplurality of predefined PER values to a respective plurality ofpredefined MSDU delivery ratio values.

Example 28 includes the subject matter of any one of Examples 19-27, andoptionally, wherein the apparatus is configured to cause the AP todetermine a Guaranteed Flow Bit Rate (GFBR) of the cellular QoS trafficflow based on a minimum data rate field in a QoS characteristics elementin the SCS descriptor element.

Example 29 includes the subject matter of any one of Examples 19-28, andoptionally, wherein the apparatus is configured to cause the AP todetermine a Guaranteed Flow Bit Rate (GFBR) and a Maximal Flow Bit Rate(MFBR) of the cellular QoS traffic flow based on a mean data rate fieldin a QoS characteristics element in the SCS descriptor element.

Example 30 includes the subject matter of any one of Examples 19-29, andoptionally, wherein the apparatus is configured to cause the AP todetermine a resource type of the cellular QoS traffic flow based on aresource type field in the SCS descriptor element.

Example 31 includes the subject matter of Example 30, and optionally,wherein the resource type field comprises a value from a plurality ofpredefined resource type field values, the plurality of predefinedresource type field values comprising a first resource type field valueto indicate a Guaranteed Bit Rate (GBR) flow, a second resource typefield value to indicate a non-GBR flow, and a third resource type fieldvalue to indicate a GBR-delay critical flow.

Example 32 includes the subject matter of any one of Examples 19-31, andoptionally, wherein the set of the plurality QoS parameters comprises atleast one of a resource type, a priority level, a Packet Delay Budget(PDB), a Packet Error Rate (PER), an averaging window, or a Maximum DataBurst Volume (MDBV).

Example 33 includes the subject matter of any one of Examples 19-32, andoptionally, wherein the SCS descriptor element comprises an elementidentifier (ID) field, a length field after the element ID field, an SCSID field after the length field, and a request type field after theSCSID field, wherein the cellular QoS index field is after the SCSIDfield.

Example 34 includes the subject matter of any one of Examples 19-33, andoptionally, wherein the cellular QoS index field comprises a fifthgeneration (5G) QoS Index (5QI) field.

Example 35 includes the subject matter of any one of Examples 19-34, andoptionally, comprising a radio to receive the SCS request.

Example 36 includes the subject matter of Example 35, and optionally,comprising one or more antennas connected to the radio, and a processorto execute instructions of an operating system of the AP.

Example 37 comprises a wireless communication device comprising theapparatus of any of Examples 1-36.

Example 38 comprises an apparatus comprising means for executing any ofthe described operations of any of Examples 1-36.

Example 39 comprises a product comprising one or more tangiblecomputer-readable non-transitory storage media comprising instructionsoperable to, when executed by at least one processor, enable the atleast one processor to cause a wireless communication device to performany of the described operations of any of Examples 1-36.

Example 40 comprises an apparatus comprising: a memory interface; andprocessing circuitry configured to: perform any of the describedoperations of any of Examples 1-36.

Example 41 comprises a method comprising any of the described operationsof any of Examples 1-36.

Functions, operations, components and/or features described herein withreference to one or more aspects, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other aspects, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

What is claimed is:
 1. An apparatus comprising logic and circuitryconfigured to cause a wireless communication station (STA) to: set acellular Quality of Service (QoS) index value in a cellular QoS indexfield to indicate a predefined setting of a set of a plurality QoSparameters for a cellular QoS traffic flow to be communicated by the STAover a Wireless Local Area Network (WLAN); and transmit a StreamClassification Service (SCS) request to an Access Point (AP) of theWLAN, the SCS request comprising an SCS descriptor element, the SCSdescriptor element comprising the cellular QoS index field.
 2. Theapparatus of claim 1, wherein the SCS descriptor element comprises avendor specific element, the vendor specific element comprising thecellular QoS index field.
 3. The apparatus of claim 2, wherein thevendor specific element comprises at least one of a resource type field,or a priority field, wherein the resource type field is configured toindicate a resource type of the cellular QoS traffic flow, wherein thepriority field is configured to indicate a priority of the cellular QoStraffic flow.
 4. The apparatus of claim 1, wherein the SCS descriptorelement comprises a QoS characteristics element, the QoS characteristicselement comprising the cellular QoS index field.
 5. The apparatus ofclaim 4, wherein QoS characteristics element comprises at least one of aresource type field, or a priority field, wherein the resource typefield is configured to indicate a resource type of the cellular QoStraffic flow, wherein the priority field is configured to indicate apriority of the cellular QoS traffic flow.
 6. The apparatus of claim 1configured to cause the STA to set a delay bound field based on a PacketDelay Budget (PDB) of the cellular QoS traffic flow, wherein the SCSdescriptor element comprises a QoS characteristics element, the QoScharacteristics element comprising the delay bound field.
 7. Theapparatus of claim 6 configured to cause the STA to set a value in thedelay bound field based on a subtraction result of subtracting a CoreNetwork PDB (CN-PDB) from the PDB of the cellular QoS traffic flow. 8.The apparatus of claim 1 configured to cause the STA to set a MediumAccess Control (MAC) Service Data Unit (MSDU) delivery ratio field basedon a Packet Error Rate (PER) of the cellular QoS traffic flow, whereinthe SCS descriptor element comprises a QoS characteristics element, theQoS characteristics element comprising the MSDU delivery ratio field. 9.The apparatus of claim 8 configured to cause the STA to set a value inthe MSDU delivery ratio field according to a predefined mapping table,the mapping table configured to map a plurality of predefined PER valuesto a respective plurality of predefined MSDU delivery ratio values. 10.The apparatus of claim 1 configured to cause the STA to set a minimumdata rate field based on a Guaranteed Flow Bit Rate (GFBR) of thecellular QoS traffic flow, wherein the SCS descriptor element comprisesa QoS characteristics element, the QoS characteristics elementcomprising the minimum data rate field.
 11. The apparatus of claim 1configured to cause the STA to set a mean data rate field based on anaverage of a Guaranteed Flow Bit Rate (GFBR) and a Maximal Flow Bit Rate(MFBR) of the cellular QoS traffic flow, wherein the SCS descriptorelement comprises a QoS characteristics element, the QoS characteristicselement comprising the mean data rate field.
 12. The apparatus of claim1 configured to cause the STA to set a resource type field in the SCSdescriptor element to indicate a resource type of the cellular QoStraffic flow.
 13. The apparatus of claim 12 configured to cause the STAto set the resource type field to a value from a plurality of predefinedresource type field values, the plurality of predefined resource typefield values comprising a first resource type field value to indicate aGuaranteed Bit Rate (GBR) flow, a second resource type field value toindicate a non-GBR flow, and a third resource type field value toindicate a GBR-delay critical flow.
 14. The apparatus of claim 1,wherein the SCS descriptor element comprises an element identifier (ID)field, a length field after the element ID field, an SCS ID field afterthe length field, and a request type field after the SCSID field,wherein the cellular QoS index field is after the SCSID field.
 15. Theapparatus of claim 1, wherein the cellular QoS index field comprises afifth generation (5G) QoS Index (5QI) field.
 16. The apparatus of claim1 comprising a radio to transmit the SCS request, one or more antennasconnected to the radio, and a processor to execute instructions of anoperating system of the STA.
 17. A product comprising one or moretangible computer-readable non-transitory storage media comprisinginstructions operable to, when executed by at least one processor,enable the at least one processor to cause a wireless communicationstation (STA) to: set a cellular Quality of Service (QoS) index value ina cellular QoS index field to indicate a predefined setting of a set ofa plurality QoS parameters for a cellular QoS traffic flow to becommunicated by the STA over a Wireless Local Area Network (WLAN); andtransmit a Stream Classification Service (SCS) request to an AccessPoint (AP) of the WLAN, the SCS request comprising an SCS descriptorelement, the SCS descriptor element comprising the cellular QoS indexfield.
 18. The product of claim 17, wherein the SCS descriptor elementcomprises a vendor specific element, the vendor specific elementcomprising the cellular QoS index field.
 19. An apparatus for a wirelesscommunication station (STA), the apparatus comprising: means for settinga cellular Quality of Service (QoS) index value in a cellular QoS indexfield to indicate a predefined setting of a set of a plurality QoSparameters for a cellular QoS traffic flow to be communicated by the STAover a Wireless Local Area Network (WLAN); and means for causing the STAto transmit a Stream Classification Service (SCS) request to an AccessPoint (AP) of the WLAN, the SCS request comprising an SCS descriptorelement, the SCS descriptor element comprising the cellular QoS indexfield.
 20. The apparatus of claim 19, wherein the SCS descriptor elementcomprises a vendor specific element, the vendor specific elementcomprising the cellular QoS index field.